<cfcomponent extends="queries">

	<!---Need to call BASE functions--->
    <cfset BASE = CreateObject("component", "base") />
    
    <!--- THIS WILL CHANGE FROM SP WHEN SCF STARTS USING NEW BADGE SOFTWARE --->
    <!--- Step4 Update BadgeID  --->
    <cffunction name="funcUpdateBadgeNo" returntype="void">    
        <cfargument default="-1" name="EmpID" required="yes" />
        <cfargument default="-1" name="BadgeNo"  required="yes" />
        
        <cfquery name="qryUpdateBadgeNo" datasource="#Session.DataSourceRosetta#">
            scf_UpdateBadgeNo #ARGUMENTS.EmpID#, #ARGUMENTS.BadgeNo#    
        </cfquery>
        
    </cffunction>
    <!--- Step4 Update BadgeID  --->
    <!--- THIS WILL CHANGE FROM SP WHEN SCF STARTS USING NEW BADGE SOFTWARE --->
    
    
    
    <!--- THIS IS A HUGE SP AND WILL TAKE A FEW DAYS TO PARSE OUT INTO CF CODE.  
    I WILL FIX THIS UGLINESS WHEN I START EPAR V2 MVC --->
    <!--- Step4 Update Employee  --->
    <cffunction name="funcUpdateEmployee" returntype="void">
        <cfargument default="-1" name="EmpID" required="yes" />
        <cfargument default="-1" name="BadgeNo" required="yes" />
        
        <cfquery name="qryUpdateEmployee" datasource="EPAR">
            scf_UpdateEmployee #ARGUMENTS.EmpID#, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 
                NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 
                NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, #ARGUMENTS.BadgeNo# 
        </cfquery>

    </cffunction>
    <!--- Step4 Update Employee  --->

    
</cfcomponent>